Mote-associated log creation

ABSTRACT

Methods and/or systems relating to mote networks having one or more logs.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to, claims the earliest available effective filing date(s) from (e.g., claims earliest available priority dates for other than provisional patent applications; claims benefits under 35 USC § 119(e) for provisional patent applications), and incorporates by reference in its entirety all subject matter of the following listed application(s); the present application also claims the earliest available effective filing date(s) from, and also incorporates by reference in its entirety all subject matter of any and all parent, grandparent, great-grandparent, etc. applications of the following listed application(s):

1. United States patent application entitled TRANSMISSION OF MOTE-ASSOCIATED LOG DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed substantially contemporaneously herewith. 2. United States patent application entitled AGGREGATING MOTE-ASSOCIATED LOG DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed substantially contemporaneously herewith. 3. United States patent application entitled TRANSMISSION OF AGGREGATED MOTE-ASSOCIATED LOG DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed substantially contemporaneously herewith. 4. United States patent application entitled FEDERATING MOTE-ASSOCIATED LOG DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed substantially contemporaneously herewith. 5. United States patent application entitled MOTE-ASSOCIATED INDEX CREATION, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed 31 Mar. 2004. 6. United States patent application entitled TRANSMISSION OF MOTE-ASSOCIATED INDEX DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed 31 Mar. 2004. 7. United States patent application entitled AGGREGATING MOTE-ASSOCIATED INDEX DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed 31 Mar. 2004. 8. United States patent application entitled TRANSMISSION OF AGGREGATED MOTE-ASSOCIATED INDEX DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed 31 Mar. 2004. 9. United States patent application entitled FEDERATING MOTE-ASSOCIATED INDEX DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed 31 Mar. 2004. 10. United States patent application entitled MOTE NETWORKS HAVING DIRECTIONAL ANTENNAS, naming Clarence T. Tegreene as inventor, filed 31 Mar. 2004. 11. United States patent application entitled MOTE NETWORKS USING DIRECTIONAL ANTENNA TECHNIQUES, naming Clarence T. Tegreene as inventor, filed 31 Mar. 2004.

TECHNICAL FIELD

The present application relates, in general, to motes.

SUMMARY

In one aspect, a method includes but is not limited to: determining at least one of sensing information or control information of a device at a mote; and creating one or more mote-addressed content logs having at least one device identifier associated with the device in response to said determining. In addition to the foregoing, other method aspects are described in the claims, drawings, and/or text forming a part of the present application.

In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.

In one aspect, a system includes but is not limited to: at least one mote-appropriate device; and at least one log creation agent resident in a mote, said at least one log creation agent configured to create at least one of a sensing/control log or a routing/spatial log. In addition to the foregoing, other system aspects are described in the claims, drawings, and/or text forming a part of the present application.

In one aspect, a system includes but is not limited to: at least one mote-appropriate device; and a mote-addressed content log having at least one of sensing/control information or routing/spatial information in association with a device identifier of the at least one mote-appropriate device. In addition to the foregoing, other system aspects are described in the claims, drawings, and/or text forming a part of the present application.

In addition to the foregoing, various other method and/or system aspects are set forth and described in the text (e.g., claims and/or detailed description) and/or drawings of the present application.

The foregoing is a summary and thus contains, by necessity, simplifications, generalizations and omissions of detail; consequently, those skilled in the art will appreciate that the summary is illustrative only and is NOT intended to be in any way limiting. Other aspects, inventive features, and advantages of the devices and/or processes described herein, as defined by the claims, will become apparent in the detailed description set forth herein.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows an example of mote 100 of mote-appropriate network 150 that may serve as a context for introducing one or more processes and/or devices described herein.

FIG. 2 depicts an exploded view of mote 200 that forms a part of a mote-appropriate network (e.g., as shown in FIGS. 3, 4, 5, 7, 8, 10, 11 and/or 12).

FIG. 3 depicts an exploded view of mote 300 forming a part of mote-appropriate network 350 that may serve as a context for introducing one or more processes and/or devices described herein.

FIG. 4 shows a high-level diagram of a network having a first set of motes addressed 1A through MA (M is an integer greater than 1; A is the letter A and in some instances is used herein to help distinguish differently administered networks such as shown/described in relation to FIGS. 10, 11, and/or 12), which may form a context for illustrating one or more processes and/or devices described herein.

FIG. 5 depicts an exploded view of mote 500 forming a part of mote-appropriate network 550 that may serve as a context for introducing one or more processes and/or devices described herein.

FIG. 6 depicts an exploded view of mote 600 forming a part of mote-appropriate network 550 (FIG. 5) that may serve as a context for introducing one or more processes and/or devices described herein.

FIG. 7 shows a high-level diagram of an exploded view of a mote appropriate network that depicts a first set of motes addressed 1A through MA (M is an integer greater than 1; A is the letter A and in some instances is used herein to help distinguish differently administered networks as in FIGS. 11 and/or 12), which may form an environment for process(es) and/or device(s) described herein.

FIG. 8 shows an exploded view of aggregation 710 of content logs of FIG. 7. Aggregation 710 of content logs is shown as having mote addressed content logs for motes 1A through MA for times t=t0 (an initial time) through and up to time=tcurrent (a current time).

FIG. 9 depicts an exploded view of aggregation 710 of content logs of FIG. 7.

FIG. 10 shows a high-level diagram of first-administered set 1000 of motes addressed 1A through MA, and second-administered set 1002 of motes addressed 1B through NB (M and N are integers greater than 1; A and B are letters used herein to help distinguish differently administered networks as in FIGS. 10, 11 and 12) that may form an environment for process(es) and/or device(s) described herein.

FIG. 11 shows a high-level diagram of first-administered set 1000 of motes and second-administered set 1002 of motes modified in accordance with teachings of subject matter described herein.

FIG. 12 shows the high-level diagram of FIG. 11, modified to show first-administered set 1000 of motes and second-administered set 1002 of motes wherein each mote is illustrated as having log(s) (e.g., mote-addressed and/or multi-mote) and associated reporting entity(ies).

FIG. 13 shows an exemplary exploded view of federated log 916.

The use of the same symbols in different drawings typically indicates similar or identical items.

DETAILED DESCRIPTION

The present application uses formal outline headings for clarity of presentation. However, it is to be understood that the outline headings are for presentation purposes, and that different types of subject matter may be discussed throughout the application (e.g., device(s)/structure(s) may be described under process(es)/operations heading(s) and/or process(es)/operations may be discussed under structure(s)/process(es) headings; and/or descriptions of single topics may span two or more topic headings). Hence, the use of the formal outline headings is not intended to be in any way limiting.

I. Mote-Associated Log Creation

A. Structure(s) and/or System(s)

With reference now to FIG. 1, shown is an example of mote 100 of mote-appropriate network 150 that may serve as a context for introducing one or more processes and/or devices described herein. A mote is typically composed of sensors, actuators, computational entities, and/or communications entities formulated, in most cases at least in part, from a substrate. As used herein, the term “mote” typically means a semi-autonomous computing, communication, and/or sensing device as described in the mote literature (e.g., Intel Corporation's mote literature), as well as equivalents recognized by those having skill in the art (e.g., Intel Corporation's smart dust projects). Mote 100 depicts a specific example of a more general mote. Mote 100 is illustrated as having antenna 102, physical layer 104, antenna entity 119, network layer 108 (shown for sake of example as a mote-appropriate ad hoc routing application), light device entity 110, electrical/magnetic device entity 112, pressure device entity 114, temperature device entity 116, volume device entity 118, and inertial device entity 120. Light device entity 110, electrical/magnetic device entity 112, pressure device entity 114, temperature device entity 116, volume device entity 118, antenna entity 119, and inertial device entity 120 are depicted to respectively couple through physical layers 104 with light device 140, electrical/magnetic device 142, pressure device 144, temperature device 156, volume device 158, antenna 102, and inertial device 160. Those skilled in the art will appreciate that the herein described entities and/or devices are illustrative, and that other entities and/or devices consistent with the teachings herein may be substituted and/or added.

Those skilled in the art will appreciate that herein the term “device,” as used in the context of devices comprising or coupled to a mote, is intended to represent but is not limited to transmitting devices and/or receiving devices dependent on context. For instance, in some exemplary contexts light device 140 is implemented using one or more light transmitters (e.g., coherent light transmission devices or non-coherent light transmission devices) and/or one or more light receivers (e.g., coherent light reception devices or non-coherent light reception devices) and/or one or more supporting devices (e.g., optical filters, hardware, firmware, and/or software). In some exemplary implementations, electrical/magnetic device 142 is implemented using one or more electrical/magnetic transmitters (e.g., electrical/magnetic transmission devices) and/or one or more electrical/magnetic receivers (e.g., electrical/magnetic reception devices) and/or one or more supporting devices (e.g., electrical/magnetic filters, supporting hardware, firmware, and/or software). In some exemplary implementations, pressure device 144 is implemented using one or more pressure transmitters (e.g., pressure transmission devices) and/or one or more pressure receivers (e.g., pressure reception devices) and/or one or more supporting devices (e.g., supporting hardware, firmware, and/or software). In some exemplary implementations, temperature device 156 is implemented using one or more temperature transmitters (e.g., temperature transmission devices) and/or one or more temperature receivers (e.g., temperature reception devices) and/or one or more supporting devices (e.g., supporting hardware, firmware, and/or software). In some exemplary implementations, volume device 158 is implemented using one or more volume transmitters (e.g., gas/liquid transmission devices) and/or one or more volume receivers (e.g., gas/liquid reception devices) and/or one or more supporting devices (e.g., supporting hardware, firmware, and/or software). In some exemplary implementations, inertial device 160 is implemented using one or more inertial transmitters (e.g., inertial force transmission devices) and/or one or more inertial receivers (e.g., inertial force reception devices) and/or one or more supporting devices (e.g., supporting hardware, firmware, and/or software). Those skilled in the art will recognize that although a quasi-stack architecture is utilized herein for clarity of presentation, other architectures may be substituted in light of the teachings herein. In addition, although not expressly shown, those having skill in the art will appreciate that entities and/or functions associated with concepts underlying Open System Interconnection (OSI) layer 2 (data link layers) and OSI layers 4-6 (transport-presentation layers) are present and active to allow/provide communications consistent with the teachings herein. Those having skill in the art will appreciate that these layers are not expressly shown/described herein for sake of clarity.

Referring now to FIG. 2, depicted is an exploded view of mote 200 that forms a part of a mote-appropriate network (e.g., as shown in FIGS. 3, 4, 5, 7, 8, 10, 11 and/or 12). Mote 200 is illustrated as similar to mote 100 (FIG. 1), but with the addition of log creation agent 202, mote-addressed sensing/control log 204, and mote-addressed routing/spatial log 252.

Mote-addressed sensing/control log 204 is shown in FIG. 2 as having illustrative entries of light device information, electrical/magnetic device information, pressure device information, temperature device information, volume device information, inertial device information, and antenna information. Examples of light device information include measures of brightness, saturation, intensity, color, hue, power (e.g., watts), flux (e.g., lumens), irradiance (e.g., Watts/cm²), illuminance (lumens/m², lumens/ft²), pixel information (e.g., numbers of pixels (e.g., one for a very small mote image capture device), relative pixel orientation)), etc. Examples of electrical/magnetic device information include measures of field strength, flux, current, voltage, etc. Examples of pressure device information include measures of gas pressure, fluid pressure, radiation pressure, mechanical pressure, etc. Examples of temperature device information include measures of temperature such as Kelvin, Centigrade, and Fahrenheit, etc. Examples of inertial device information include measures of force, measures of acceleration, deceleration, etc. Examples of antenna information include measures of signal power, antenna element position, relative phase orientations of antenna elements, delay line configurations of antenna elements, beam directions, field of regard directions, antenna types (e.g., horn, biconical, array, Yagi, log-periodic, etc.), etc.

FIG. 2 does not show illustrative entries for mote-addressed routing/spatial log 252. For a specific example of what one implementation of a mote-addressed routing/spatial log might contain, see the mote-addressed routing/spatial logs shown internal to multi-mote content log 504 of FIG. 5. As shown in FIG. 5, in some implementations a mote-addressed routing/spatial log will contain a listing of mote addresses directly accessible from a mote (e.g., via direct radio transmission/reception from/by antenna 102), an assessment of qualities of data communications service on the data communication links to such directly accessible motes, and/or a listing of relative and/or absolute spatial coordinates of such directly accessible motes.

Continuing to refer to FIG. 2, in one implementation, log creation agent 202 is a computer program—resident in mote 200—that executes on a processor of mote 200 and that constructs and/or stores mote-addressed sensing/control log 204, and/or mote-addressed routing/spatial log 252 in memory of mote 200. In some implementations, log creation agent 202 is pre-installed on mote 200 prior to mote 200 being added to a mote-appropriate network, while in other implementations log creation agent 202 crawls and/or is transmitted to mote 200 from another location (e.g., a log creation agent at another mote or another networked computer (not shown) clones itself and sends that clone to mote 200). In yet other implementations, log creation agent 202 is installed at a proxy (not shown) for mote 200.

The inventors point out that in some applications the systems and/or processes transfer their instructions in a piecewise fashion over time, such as is done in the mote-appropriate Mate′ virtual machine of the related art. The inventors also point out that in some applications motes are low-power and/or low bandwidth devices, and thus in some implementations the system(s) and process(es) described herein allow many minutes (e.g., hours, days, or even weeks) for herein described agents and/or processes to migrate to and establish themselves at various motes. The same may also hold true for transmission of information among motes in that in some implementations such transmission may be done over the course of hours, days, or even weeks depending upon bandwidth, power, and/or other constraints. In other implementations, the migrations and/or transmissions are accomplished more rapidly, and in some cases may be accomplished as rapidly as possible.

For sake of clarity, some implementations shown/described herein include various separate architectural components. Those skilled in the art will appreciate that the separate architectural components are so described for sake of clarity, and are not intended to be limiting. Those skilled in the art will appreciate the herein-described architectural components, such reporting entities, logs, and/or device entities, etc. are representative of substantially any architectural components that perform in a similar manner. For example, while some implementations show reporting entities obtaining information from logs created with device entity data, those skilled in the art will appreciate that such implementations are representative of reporting entities obtaining the data directly from the device entities. As another example, while some implementations show reporting entities obtaining information produced by device entities, those skilled in the art will appreciate that such implementations are representative of queries executing at the mote that extract and/or transmit similar information as that described in the relation to the reporting entities and/or device entities (e.g., some multi-mote creation agent making a query of a database entity resident at a mote, where the database entity would perform in a fashion similar to that described in relation to reporting entities, logs, and/or device entities, etc.). Thus, those skilled in the art will appreciate that the architectural components described herein are representative of virtually any grouping of architectural components that perform in a similar manner.

B. Process(es) and/or Scheme(s)

Mote 200 of FIG. 2 can serve as a context in which one or more processes and/or devices may be illustrated. In one exemplary process, once log creation agent 202 has become active at mote 200, log creation agent 202 communicates with device entity registry 210 to receive device identifiers indicative of device entities present at mote 200 (e.g., light device entity 110, electrical/magnetic device entity 112, pressure device entity 114, etc.). In some implementations, device entities of mote 200 register their presences with device entity registry 210, while in other implementations the operating system of mote 200 registers the device entities when the operating system installs the device entities and/or their associated drivers (if any). In some implementations, device entity registry 210 receives device identifiers from an external source (e.g., receiving the device identifiers from a multi-mote creation agent, an aggregation agent, or a federation agent that transmits over a wireless link). In some implementations, once log creation agent 202 becomes aware of what device entities are present, log creation agent 202 communicates with the device entities (e.g., light device entity 110, electrical/magnetic entity 112, pressure entity 114, etc.) to find out what sensing/control functions are present and/or available at their various respectively associated devices (e.g., light device 140, electrical/magnetic device 142, pressure device 144, etc.). In some implementations, log creation agent 202 also communicates with routing/spatial log 252 to find out the mote-network address of mote 200 (e.g., mote-network address 6A) as well as other spatial information (e.g., mote-network addresses and/or spatial locations of the motes that can be reached directly by wireless link from mote 200; spatial locations may be absolute and/or relative to some marker, such as mote 200 itself). In some implementations, log creation agent 202 communicates with the device entities using a common application protocol which specifies standard interfaces that allow log creation agent 202 to garner the necessary information without knowing the internal workings and/or architectures of each specific device entity. In other implementations, such a common application protocol is not used.

In various implementations, contemporaneous with and/or subsequent to log creation agent 202 communicating with the device entities, log creation unit 202 creates one or more mote-addressed content logs. In some implementations the one or more mote-addressed content logs are associated with the mote-network address of the mote at which log creation unit 202 resides. The inventors point out that examples of the term “log,” and/or phrases containing the term “log,” exist in the text (e.g., independent claims, dependent claims, detailed description, and/or summary) and/or drawings forming the present application and that such term and/or phrases may have scopes different from like terms and/or phrases used in other contexts. In some implementations the one or more mote-addressed content logs are time stamped with the time the log was created. Mote 200 is depicted for sake of illustration as having a mote-address of 6A. Accordingly, a specific example of more general mote-addressed content logs is shown in FIG. 2 as mote 6A-addressed sensing/control log 204. Mote 6A-addressed sensing/control log 204 is depicted as listing the sensing and/or control information in association with device-identifiers associated with devices present and/or available at mote 200. Mote 6A-addressed sensing/control log 204 is also depicted for sake of illustration as having been created at the current time, and thus is shown stamped with the denotation “tcurrent.” In addition, shown as yet another specific example of more general mote-addressed content logs is mote 6A-addressed routing/spatial log 252, which typically contains a listing of mote-network addresses of those motes directly accessible from mote 200 and such directly accessible motes' spatial orientations relative to mote 200 and/or some other common spatial reference location (e.g., GPS). Mote 6A-addressed routing/spatial log 252 is also depicted as having a time stamp of “tcurrent,” In some implementations, log creation unit 202 creates one or more extensible mote-addressed content logs (e.g., creating the one or more extensible logs in response to a type of content being logged). In addition, those having skill in the art will appreciate that while direct mote addressing is shown and described herein for sake of clarity (e.g., mote-appropriate network addresses), the mote addressing described herein may also entail indirect addressing, dependent upon context. Examples of indirect addressing include approaches where a mote-address encodes an address of an agent that in turn produces the address of the mote (analogous to the Domain Name System in the Internet), or where the mote-address directly or indirectly encodes a route to a mote (analogous to explicit or implicit routable addresses.). Those having skill in the art will appreciate that adapting the teachings herein to indirect addressing may be done with a reasonable amount of experimentation, and that such adaptation is not expressly set forth herein for sake of clarity.

As noted herein, a content log may have a device identifier which in various implementations may include an implicit and/or explicit indicator used to reference the specific device at that mote. Those having skill in the art will appreciate that ways in which such may be achieved include the use of a structured name. Those having skill in the art will appreciate that in some implementations mote-local devices may also have global addresses, which may be substituted or allowed to “stand in” for mote addresses.

II. Transmission of Mote-Associated Log Data

A. Structure(s) and/or System(s)

With reference now to FIG. 3, depicted is an exploded view of mote 300 forming a part of mote-appropriate network 350 that may serve as a context for introducing one or more processes and/or devices described herein. Mote 300 is illustrated as similar to mote 200 (FIG. 2), but with the addition of reporting entity 302. In some implementations, reporting entity 302 is a computer program—resident in mote 300—that executes on a processor of mote 300 and that transmits all or a part of mote-addressed sensing/control log 204, and/or mote-addressed routing/spatial log 252 to another entity (e.g., through antenna 102 to a multi-mote log creation agent such as shown/described in relation to FIG. 5 or through a mote-network to a designated gateway such as shown/described in relation to FIGS. 7, 8, 11, and/or 12). In some implementations, reporting entity 302 is pre-installed on mote 300 prior to mote 300 being added to a mote-appropriate network, while in other implementations reporting entity 302 crawls and/or is transmitted to mote 300 from another location (e.g., a reporting entity at another mote or another networked computer (not shown) clones itself and sends that clone to mote 300). The inventors point out that in some applications the crawling and/or transmissions described herein are performed in a piecewise fashion over time, such as is done in the mote-appropriate Mate′ virtual machine of the related art. The inventors also point out that in some applications motes are low-power and/or low bandwidth devices, and thus in some implementations the crawling and/or transmissions described herein allow many minutes (e.g., hours, days, or even weeks) for herein described agents and/or processes to migrate to and establish themselves at various motes. The same may also hold true for transmission of information among motes in that in some implementations such transmission may be done over the course of hours, days, or even weeks depending upon bandwidth, power, and/or other constraints. In other implementations, the migrations and/or transmissions are accomplished more rapidly, and in some cases may be accomplished as rapidly as possible.

B. Process(es) and/or Scheme(s)

Mote 300 of FIG. 3 can serve as a context in which one or more processes and/or devices may be illustrated. In one exemplary process, reporting entity 302 transmits at least a part of a content log to another entity either resident within or outside of mote network 350 (e.g., through antenna 102 to a multi-mote log creation agent such as shown/described in relation to FIG. 5 or through a mote-network to a designated gateway-proximate mote as shown/described in relation to FIGS. 5, 6, 7, 8, 9, 11 and/or 12). In some implementations, reporting entity 302 transmits in response to a received schedule (e.g., received from multi-mote log creation agent 502 of FIG. 5 and/or federated log creation agent 914 of FIGS. 11 and/or 12). In some implementations, reporting entity 302 transmits in response to a derived schedule. In some implementations, the schedule is derived in response to one or more optimized queries. In some implementations, the schedule is derived in response to one or more stored queries (e.g., previously received or generated queries).

In some implementations, reporting entity 302 transmits in response to a received query (e.g., received from multi-mote log creation agent of FIG. 5 and/or federated log creation agent of FIG. 9 or 10). In various implementations, reporting entity 302 transmits using either or both public key and private key encryption techniques. In various other implementations, reporting entity 302 decodes previously encrypted data, using either or both public key and private key encryption techniques, prior to the transmitting.

Referring now to FIG. 4, shown is a high-level diagram of a network having a first set of motes addressed 1A through MA (M is an integer greater than 1; A is the letter A and in some instances is used herein to help distinguish differently administered networks such as shown/described in relation to FIGS. 10, 11, and/or 12), which may form a context for illustrating one or more processes and/or devices described herein. Each mote is shown as having a mote-addressed content log that includes a sensing/control log and/or a routing/spatial log respectively associated with the sensing/control information at each such mote and/or the spatial locations (relative and/or absolute) of motes that can be reached by direct transmission from each such mote. In some implementations, the motes' various logs are created and/or function in fashions similar to logs shown/described elsewhere herein (e.g., in relation to FIG. 3). In addition, shown is that the motes of FIG. 4 include reporting entities that are created and/or function in ways analogous to the creation and/or functioning of reporting entities as shown and described elsewhere herein (e.g., in relation to FIG. 3). In addition, although not explicitly shown, one or more of the motes of FIG. 4 may include log creation agents that are created and/or function in ways analogous to the creation and/or functioning of log creation agents as shown and described elsewhere herein (e.g., in relation to FIG. 2). In some implementations, the reporting entities at each mote transmit all or a part of their mote-addressed content logs (e.g., mote-addressed sensing/control logs, and/or mote-addressed routing/spatial logs) to one or more entities (e.g., multi-mote log creation agent 502 such as shown/described in relation to FIG. 5 and/or multi-mote log creation agent 716 such as shown/described in relation to FIGS. 7, 9 and 10). In some implementations, such transmissions are done in response to a schedule, and in other implementations such transmissions are done in response to queries from the one or more entities. Such transmissions may be in response to received schedules, in response to schedules derived at least in part from optimized queries, in response to schedules derived at least in part from received queries, and/or in response to received queries such as described here and/or elsewhere herein.

III. Aggregating Mote-Associated Log Data

A. Structure(s) and/or System(s)

With reference now to FIG. 5, depicted is an exploded view of mote 500 forming a part of mote-appropriate network 550 that may serve as a context for introducing one or more processes and/or devices described herein. Mote 500 is illustrated as similar to mote 300 (FIG. 3), but with the addition of multi-mote log creation agent 502, multi-mote content log 504, and multi-mote registry 510 (e.g., a registry of motes under the aegis of multi-mote log creation agent 502 and/or from which multi-mote content log 504 is to be constructed). Multi-mote content log 504 typically contains at least a part of content logs from at least two differently-addressed motes. As an example of the foregoing, multi-mote content log 504 is shown containing sensing/control mote-addressed logs and mote-addressed routing/spatial logs for two differently addressed motes: a mote having mote-network address of 1A and a mote having a mote-network address of 3A. In some implementations, the sensing/control logs and/or routing/spatial logs function more or less analogously to mote-addressed sensing/content log 204, and/or mote-addressed routing/spatial log 252 of mote 200 (e.g., as shown/described in relation to FIG. 2). In some implementations, multi-mote log creation agent 502 is a computer program—resident in mote 500—that executes on a processor of mote 500 and that constructs and stores multi-mote content log 504 in memory of mote 500. In some implementations, multi-mote log creation agent 502 is pre-installed on mote 500 prior to mote 500 being added to a mote-appropriate network, while in other implementations multi-mote log creation agent 502 crawls and/or is transmitted to mote 500 from another location (e.g., a multi-mote log creation agent at another mote or another networked computer (not shown) clones itself and sends that clone to mote 500). The inventors point out that in some applications the crawling and/or transmissions described herein are performed in a piecewise fashion over time, such as is done in the mote-appropriate Mate′ virtual machine of the related art. The inventors also point out that in some applications motes are low-power and/or low bandwidth devices, and thus in some implementations the crawling and/or transmissions described herein allow many minutes (e.g., hours, days, or even weeks) for herein described agents and/or processes to migrate to and establish themselves at various motes. The same may also hold true for transmission of information among motes in that in some implementations such transmission may be done over the course of hours, days, or even weeks depending upon bandwidth, power, and/or other constraints. In other implementations, the migrations and/or transmissions are accomplished more rapidly, and in some cases may be accomplished as rapidly as possible.

B. Process(es) and/or Scheme(s)

Mote 500 of FIG. 5 can serve as a context in which one or more processes and/or devices may be illustrated. In one exemplary process, once multi-mote log creation agent 502 has become active at mote 500, multi-mote log creation agent 502 obtains a listing of motes from which multi-mote content log 504 is to be constructed (e.g., a listing of motes making up a part of mote network 550). In some implementations, multi-mote log creation agent 502 obtains the listing of motes from which multi-mote content log 504 is to be constructed by communicating with multi-mote registry 510 to learn what mote-network addresses multi-mote log creation agent 502 is to consult to create multi-mote content log 504. In some implementations, various log creation agents at various respective motes (e.g., the log creation agents at the motes of FIG. 4) register their mote addresses with multi-mote registry 510, while in other implementations an administrator (e.g., either at or remote from mote 500) registers the mote-addresses in multi-mote registry 510. In some implementations, a system administrator places various motes under the aegis of particular multi-mote log creation agents based on a single criterion or combined criteria such as spatial locations, bandwidths, qualities of service of data communication links, and/or contents of data captured at various particular motes. In other implementations, multi-mote log creation agent 502 is pre-loaded with knowledge of the listing of motes from which multi-mote content log 504 is to be constructed. In yet other implementations, the listing of motes from which multi-mote content log 504 is to be constructed is obtained from various motes that inform multi-mote log creation agent 502 that such various motes are to be included in the listing. Those having skill in the art will appreciate that other mechanisms for obtaining the listing, consistent with the teachings herein, may be substituted.

In some implementations, once multi-mote log creation agent 502 becomes aware of the mote-addresses for which it (multi-mote log creation agent 502) is responsible, multi-mote log creation agent 502 communicates with the various respective reporting entities at the various motes for which multi-mote log creation agent 502 is responsible and receives all or part of various respective mote-addressed content logs (e.g., at least a part of one or more sensing/control logs and/or one or more routing/spatial logs such as shown and described elsewhere herein). Thereafter, multi-mote log creation agent 502 uses the various reported mote-addressed content logs to construct and/or save multi-mote content log 504 by aggregating at least a part of mote-addressed content logs from two separately addressed and/or actually separate motes. For example, multi-mote content log 504 is shown as an aggregate of sensing/control and routing/spatial logs for motes having mote-network addresses of 1A and 3A, although typically multi-mote content logs will log more than just two motes.

In some implementations, multi-mote log creation agent 502 receives all or part of various respective mote-addressed content logs from various respective reporting entities at various motes which transmit in response to a schedule (e.g., once every 18 minutes). In some implementations, the schedule may be received, pre-stored, and/or derived (e.g., such as shown/described in relation to other transmissions described elsewhere herein). In addition, while the present application describes multi-mote log creation agent 502 receiving all or part of various respective mote-addressed content logs from the various respective reporting entities at the various motes (e.g., mote 1A and/or mote 3A), those having skill in the art will appreciate that in other implementations multi-mote log creation agent 502 receives all or part of such logs from one or more motes representing the first set of motes.

In various implementations discussed herein, multi-mote log creation agent 502 receives mote-addressed content logs transmitted by reporting entities of various motes from which multi-mote log creation agent 502 creates multi-mote content log 504. In other implementations, multi-mote log creation agent 502 receives one or more previously-created multi-mote content logs transmitted by multi-mote reporting entities at various motes from which multi-mote log creation agent 502 creates multi-mote content log 504. That is, in some implementations, multi-mote log creation agent 502 creates multi-mote content log 504, at least in part, from a previously generated aggregate of mote-addressed content logs (e.g., from a previously generated multi-mote content log). In some implementations, such received multi-mote content logs have been created by other multi-mote log creation agents resident at other motes throughout a mote network (e.g., a mote network such as shown in FIG. 4). Subsequent to receiving such previously created multi-mote content logs, multi-mote log creation agent 502 then aggregates the multi-mote content logs to form another multi-mote content log. In yet other implementations, multi-mote log creation agent 502 aggregates both mote-addressed content logs and multi-mote content logs respectively received from various reporting entities to create a multi-mote content log. The inventors point out that in some applications motes are low-power and/or low bandwidth devices, and thus in some implementations the systems and processes described herein allow many minutes (e.g., hours, days, or even weeks) for herein described agents and processes to migrate to and establish themselves at various motes (e.g., by transferring their instructions in a piecewise fashion over time). The same may also hold true for transmission of information among motes.

IV. Transmission of Aggregated Mote-Associated Log Data

A. Structure(s), and/or System(s)

With reference now to FIG. 6, depicted is an exploded view of mote 600 forming a part of mote-appropriate network 550 (FIG. 5) that may serve as a context for introducing one or more processes and/or devices described herein. Mote 600 is illustrated as similar to mote 500 (FIG. 5), but with the addition of multi-mote reporting entity 602. In some implementations, multi-mote reporting entity 602 is a computer program—resident in mote 600—that executes on a processor of mote 600. In some implementations, multi-mote reporting entity 602 is a computer program that is pre-installed on mote 600 prior to mote 600 being added to a mote-appropriate network, while in other implementations multi-mote reporting entity 602 is a computer program that crawls and/or is transmitted to mote 600 from another location (e.g., a reporting entity at another mote or another networked computer (not shown) clones itself and sends that clone to mote 600). The inventors point out that in some applications the crawling and/or transmissions described herein are performed in a piecewise fashion over time, such as is done in the mote-appropriate Mate′ virtual machine of the related art. The inventors also point out that in some applications motes are low-power and/or low bandwidth devices, and thus in some implementations the crawling and/or transmissions described herein allow many minutes (e.g., hours, days, or even weeks) for herein described agents and/or processes to migrate to and establish themselves at various motes. The same may also hold true for transmission of information among motes in that in some implementations such transmission may be done over the course of hours, days, or even weeks depending upon bandwidth, power, and/or other constraints. In other implementations, the migrations and/or transmissions are accomplished more rapidly, and in some cases may be accomplished as rapidly as possible.

Referring now to FIG. 7, shown is a high-level diagram of an exploded view of a mote appropriate network that depicts a first set of motes addressed 1A through MA (M is an integer greater than 1; A is the letter A and in some instances is used herein to help distinguish differently administered networks as in FIGS. 11 and/or 12), which may form an environment for process(es) and/or device(s) described herein. Each mote is shown as having a mote-addressed content log that includes a sensing/control log and/or a routing/spatial log respectively associated with the sensing/control functions of devices at each such mote and/or the spatial locations (relative and/or absolute) of motes that can be reached by direct transmission from each such mote. In some implementations, the motes' various logs are created and/or function in fashions similar to mote-addressed logs shown and described herein (e.g., in relation to FIGS. 2, 3, and/or FIG. 4). In some implementations, the motes' various logs are created and/or function in fashions similar to multi-mote content logs shown and described herein (e.g., in relation to FIGS. 5 and/or 6). For example, mote 1A (i.e., mote having mote-network address 1A) and mote 6A (i.e., mote having mote-network address 6A) are shown having multi-mote content logs 750 and 752 respectively. The multi-mote content logs are created and/or function in ways analogous to those shown and/or described elsewhere herein.

Mote 4A is shown in FIG. 7 as proximate to gateway 704 onto WAN 714 (e.g., the Internet). Multi-mote log creation agent 716 is depicted as executing on the more powerful computational systems of gateway 704 (e.g., a mini and/or mainframe computer system) to create aggregation 710 of content logs. Those having skill in the art will appreciate that aggregation 710 of content logs may be composed of multi-mote content logs and/or individual mote-addressed content logs. Those having skill in the art will appreciate that aggregations of multi-mote content logs in themselves may be considered aggregates of one or more individual mote-addressed content logs and thus types of multi-mote content logs. Those having skill in the art will appreciate that multi-mote content logs in themselves may be considered aggregates of one or more individual mote-addressed content logs and thus types of aggregations of content indexes.

With reference now to FIG. 8, shown is an exploded view of aggregation 710 of content logs of FIG. 7. Aggregation 710 of content logs is shown as having mote addressed content logs for motes 1A through MA for times t=t0 (an initial time) through and up to time=tcurrent (a current time). In general, the time entries correspond with and/or are derived from time stamps of one or more mote-addressed logs such as those described elsewhere herein.

With reference now to FIG. 9, depicted is an exploded view of aggregation 710 of content logs of FIG. 7. Aggregation 710 of content logs is shown as having mote addressed content logs for motes 1A through MA for times t=t0 (an initial time) through and up to time=tcurrent (a current time). In general, the time entries of the table correspond and/or are derived from time stamps of mote-addressed logs as described elsewhere herein. Example entries for time=t0 are shown for motes having mote-network addresses of 1A and MA. Those skilled in the art will appreciate that entries at other times could be similar to or different from those shown.

Referring now again to FIG. 7, the motes are shown having reporting entities that function analogously to other reporting entities described herein (e.g., multi-mote reporting entity 602 and/or reporting entity 302). In some implementations, such reporting entities are computer programs that execute on processors of the motes wherein such reporting entities are resident and that transmit all or a part of logs at their motes (e.g., mote-addressed content logs and/or multi-mote content logs) to other entities (e.g., multi-mote log creation agents at designated mote addresses and/or designated gateway-proximate motes). In some implementations, the reporting entities are pre-installed on the motes prior to such motes' insertion to a mote-appropriate network, while in other implementations such reporting entities crawl and/or are transmitted to their respective motes from other locations (e.g., a reporting entity at another mote or another networked computer (not shown) clones itself and sends that clone to another mote). In addition, in some implementations one or more of the reporting entities is given access to the content logs of the motes and thereafter use such access to report on the content of the motes. The multi-mote content logs and/or mote-addressed content logs may be as shown and/or described both here and elsewhere herein, and such elsewhere described material is typically not repeated here for sake of clarity

In some implementations, various reporting entities at various motes transmit in response to a schedule (e.g., once every 24 hours). In one specific example implementation, a reporting entity transmits in response to a received schedule (e.g., received from multi-mote log creation agent 716 and/or from federated log creation agent 914 of FIGS. 11 and/or 12). In another specific example implementation, a reporting entity transmits in response to a derived schedule. In another specific implementation, the schedule is derived in response to one or more optimized queries. In yet other implementations, the schedule is derived in response to one or more stored queries (e.g., previously received and/or generated queries).

In other implementations, the reporting entities transmit in response to received queries (e.g., received from multi-mote log creation agents or federated log creation agents). In various implementations, the reporting entities transmit using either or both public key and private key encryption techniques. In various other implementations, the reporting entities decode previously encrypted data, using either or both public key and private key encryption techniques, prior to the transmitting.

B. Process(es) and/or Scheme(s)

With reference now again to FIGS. 6-7 and/or FIGS. 9-13 the depicted views may serve as a context for introducing one or more processes and/or devices described herein. Some exemplary processes include the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes. In one instance, multi-mote reporting entity 602 transmits at least a part of multi-mote content log 504 to another entity (e.g., another multi-mote log creation agent at a designated mote address, or a designated gateway-proximate mote or a federated log creation agent such as shown and/or described in relation to FIGS. 7, 8, 9, 11, and/or 12). Those skilled in the art will appreciate that the foregoing specific exemplary processes are representative of more general processes taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.

In some specific exemplary processes, the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of transmitting at least a part of one or more multi-mote content logs of the first set of motes. In one instance, multi-mote reporting entity 602 transmits at least a part of at least one of a mote-addressed sensing/control log of multi-mote content log 504 to another entity (e.g., another multi-mote log creation agent at a designated mote address or a designated gateway-proximate mote or a federated log creation agent such as shown and/or described in relation to FIGS. 11 and/or 12). Those skilled in the art will appreciate that the foregoing specific exemplary processes are representative of more general processes taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.

In some specific exemplary processes, the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of transmitting at least a part of a mote-addressed routing/spatial log. In one instance, multi-mote reporting entity 602 transmits at least a part of a mote-addressed routing/spatial log of multi-mote content log 504 to another entity (e.g., another multi-mote log creation agent at a designated mote address, or a designated gateway-proximate mote, or a federated log creation agent such as shown and/or described in relation to FIGS. 7, 8, 9, 11 and/or 12). Those skilled in the art will appreciate that the foregoing specific exemplary processes are representative of more general processes taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.

In some specific exemplary processes, the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of effecting the transmitting with a reporting entity. In one instance, multi-mote reporting entity 602 is a logical process at mote 600 that transmits a part of an aggregate of one or more mote-addressed content logs (e.g., multi-mote logs and/or aggregations of other logs such as mote-addressed and multi-mote logs). Those skilled in the art will appreciate that the foregoing specific exemplary processes are representative of more general processes taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.

In some specific exemplary processes, the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of obtaining access to the one or more mote-addressed content logs of the first set of motes. In one instance, multi-mote reporting entity 602 is granted the access by an entity such as a system administrator. Those skilled in the art will appreciate that the foregoing specific exemplary processes are representative of more general processes taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.

In some specific exemplary processes, the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of effecting the transmitting in response to a schedule. In one instance, multi-mote reporting entity 602 transmits at least a part of multi-mote content log 504 in response to a schedule (e.g., once every 24 hours). Those skilled in the art will appreciate that the foregoing specific exemplary processes are representative of more general processes taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.

In some specific exemplary processes, the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of receiving the schedule. In one instance, multi-mote reporting entity 602 transmits at least a part of multi-mote content log 504 in response to a received schedule (e.g., received from multi-mote log creation agent 718 and/or a federated log creation agent 914 of FIGS. 11 and/or 12). Those skilled in the art will appreciate that the foregoing specific exemplary processes are representative of more general processes taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.

In some specific exemplary processes, the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of deriving the schedule. In one instance, multi-mote reporting entity 602 transmits at least a part of multi-mote content log 504 in response to a derived schedule (e.g., derived in response to an optimized query and/or one or more stored queries). Those skilled in the art will appreciate that the foregoing specific exemplary processes are representative of more general processes taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.

In some specific exemplary processes, the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of effecting the transmitting in response to a query. In one instance, multi-mote reporting entity 602 transmits at least a part of multi-mote content log 504 in response to a received query (e.g., received from a multi-mote log creation agent or a federated log creation agent). Those skilled in the art will appreciate that the foregoing specific exemplary processes are representative of more general processes taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.

In some specific exemplary processes, the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of encrypting utilizing at least one of a private or a public key. In one instance, multi-mote reporting entity 602 transmits at least a part of multi-mote content log 504 using either or both public key and private key encryption techniques. Those skilled in the art will appreciate that the foregoing specific exemplary processes are representative of more general processes taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.

In some specific exemplary processes, the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of decoding at least a part of one or more mote-addressed content logs utilizing at least one of a public key or a private key. In one instance, multi-mote reporting entity 602 decodes previously encrypted data, using either or both public key and private key encryption techniques, prior to the transmitting of at least a part of multi-mote content log 504. Those skilled in the art will appreciate that the foregoing specific exemplary processes are representative of more general processes taught elsewhere herein, such as in the claims filed herewith and/or elsewhere in the present application.

V. Federating Mote-Associated Log Data

A. Structure(s) and/or System(s)

Referring now to FIG. 10, shown is a high-level diagram of first-administered set 1000 of motes addressed 1A through MA, and second-administered set 1002 of motes addressed 1B through NB (M and N are integers greater than 1; A and B are letters used herein to help distinguish differently administered networks as in FIGS. 10, 11, and 12) that may form an environment for process(es) and/or device(s) described herein. In some implementations, first-administered set 1000 of motes constitutes all or part of a network under a first administrator and second-administered set 1002 of motes constitutes all or part of a network under a second administrator, where the first and/or second administrators tend not to have any significant knowledge of the internal operations of networks they don't administer. Examples in which this may be the case are where first-administered set 1000 and second-administered set 1002 are owned by different business entities, and where first-administered set 1000 and second-administered set 1002 have been constructed for two separate purposes (e.g., one set to monitor crops and the other set to monitor building systems, and thus the systems were not designed to interact with each other). In some implementations, first-administered set 1000 of motes constitutes all or part of a network under a first administrator and second-administered set 1002 of motes constitutes all or part of a network under a second administrator, where either or both of the first administrator and the second administrator has some knowledge of the networks they don't administer, but the networks are administered separately for any of a variety of reasons such as security, current employment, permissions, job function distinction, organizational affiliation, workload management, physical location, network disconnection, bandwidth or connectivity differences, etc. In some implementations, first-administered set 1000 of motes constitutes all or part of a network under a first transient administration and second-administered set 1002 of motes constitutes all or part of a network under a second transient administration, where either or both the first and second transient administrations are those such as might exist when a network partitions or a signal is lost.

The inventors have noticed that in some instances it could be advantageous for one or more systems to use resources from first-administered set 1000 of motes and second-administered set 1002 of motes. The inventors have devised one or more processes and/or devices that allow systems to use resources in such a fashion.

With reference now to FIG. 11, shown is a high-level diagram of first-administered set 1000 of motes and second-administered set 1002 of motes modified in accordance with teachings of subject matter described herein. Shown respectively proximate to first-administered set 1000 of motes and second-administered set 1002 of motes are gateways 704, 706 onto WAN 714. Gateways 704, 706 are respectively shown as having resident within them multi-mote log creation agents 716, 718 and aggregations 910, 912 of first-administered set 1000 of motes and second-administered set 1002 of motes. The gateways, multi-mote log creation agents, and aggregations are created and/or function substantially analogously to the gateways, log creation agents, and aggregations of logs described elsewhere herein (e.g., in relation to Figures), and are not explicitly described here for sake of clarity. For example, aggregation 910 of first-administered logs and aggregation 912 of second-administered logs can be composed of either or both mote-addressed and/or multi-mote content logs and in themselves can be considered instances of multi-mote content logs. Furthermore, although not expressly shown in FIG. 11 for sake of clarity, it is to be understood that in general most motes will have one or more log creation agents (e.g., multi-mote or other type), logs (e.g., multi-mote or other type), and/or reporting entities (e.g., multi-mote or other type) resident within or proximate to them (see, e.g., FIG. 12). In some implementations, the functioning and/or creation of such logs, agents, and/or entities is under the control of federated log creation agent 914. In some implementations, federated log creation agent 914, on an as-needed basis, disperses and/or activates various log creation agents and/or their associated reporting entities (e.g., as shown and described in relation to FIGS. 2, 3, and/or 4), and/or various multi-mote log creation agents and/or their associated reporting entities (e.g., as shown and described in relation to FIGS. 5, 6, and/or 7) throughout first-administered set 1000 of motes and second-administered set 1002 of motes. In some implementations, such dispersals and/or activations are done on an as-needed basis, while in other implementations such dispersals and activations are pre-programmed. In yet other implementations, the agents, logs, and/or entities are pre-programmed.

Further shown in FIG. 11 are federated log creation agent 914 and federated log 916 resident within mainframe computer system 990, which in some implementations are dispersed, created, and/or activated in fashions similar to other log creation agents and logs described herein. In some implementations, federated log creation agent 914 generates federated log 916 by obtaining at least a part of one or more logs (e.g., multi-mote or mote-addressed logs) from both first-administered set 1000 of motes and second-administered set 1002 of motes. In some implementations, federated log 916 typically includes at least a part of a content log from two differently-administered mote networks, such as first-administered set 1000 of motes and second-administered set 1002 of motes In some implementations, federated log 916 has one or more entries denoting one or more respective administrative domains of one or more content log entries (e.g., see federated log 916 of FIG. 12). In other implementations, federated log 916 has access information to one or more content logs for an administered content log (e.g., in some implementations, this is actually in lieu of a content log). In other implementations, federated log 916 has information pertaining to a currency of at least one entry of an administered content log. In other implementations, federated log 916 has information pertaining to an expiration of at least one entry of an administered content log. In other implementations, federated log 916 has metadata pertaining to an administrative domain, wherein the metadata includes at least one of an ownership indicator, an access right indicator, a log refresh indicator, or a predefined policy indicator. In other implementations, federated log 916 has an administrative domain-specific query string generated for or supplied by an administrative domain to produce an updated content log for that domain.

Continuing to refer to FIG. 11, aggregation 910 of first-administered log and aggregation 912 of second-administered log (e.g., instances of multi-mote content logs) are shown as respectively interfacing with first-administered reporting entity 902 and second-administered reporting entity 904. First-administered reporting entity 902 and/or second-administered reporting entity 904 typically are dispersed, created, and/or activated in fashions analogous to the dispersal, creation, and/or activation of other reporting entities as described elsewhere herein (e.g., in relation to FIGS. 3 and/or 6), and hence such dispersals, creations, and/or activations are not explicitly described here for sake of clarity.

In some implementations, first-administered reporting entity 902 and/or second-administered reporting entity 904 transmit all/part of their respective multi-mote content logs to federated log creation agent 914, from which federated log creation agent creates federated log 916. First-administered reporting entity 902 and/or second-administered reporting entity 904 transmit in manners analogous to reporting entities discussed elsewhere herein. For example, transmitting in response to schedules received, schedules derived, and/or queries received from federated log creation agent 914, and/or transmitting using either or both public key and private key encryption techniques and/or decoding previously encrypted data, using either or both public key and private key encryption techniques, prior to the transmitting.

In the discussion of FIG. 11, federated log creation agent 914 was described as obtaining portions of aggregations of first-administered and second-administered network logs from which federated log 916 was constructed. In other implementations, federated log creation agent 914 obtains portions of first-administered and second-administered network logs from various reporting entities dispersed throughout the first-administered and second-administered mote networks 1000, 1002 (e.g., multi-mote or other type reporting entities such as those described in relation to FIGS. 3, 6, and/or elsewhere herein). Such reporting entities and logs are implicit in FIG. 9 (e.g., since the multi-mote creation agents 716, 718 would typically interact with such reporting entities to obtain logs under the purview of such entities), but are explicitly shown and described in relation to FIG. 12. In other implementations, the various reporting entities dispersed throughout the networks report directly to federated log creation agent 914. One example of such implementations is shown and described in relation to FIG. 12.

Referring now to FIG. 12, shown is the high-level diagram of FIG. 11, modified to show first-administered set 1000 of motes and second-administered set 1002 of motes wherein each mote is illustrated as having log(s) (e.g., mote-addressed and/or multi-mote) and associated reporting entity(ies). The reporting entities may be of substantially any type described herein (e.g., multi-mote or other type) and the logs may also be of substantially any type described herein (e.g., multi-mote or mote-addressed content log).

In some implementations, various reporting entities dispersed throughout first-administered set 1000 of motes and second-administered set 1002 of motes transmit all/part of their respective logs (multi-mote or otherwise) to federated log creation agent 914, from which federated log creation agent creates federated log 916. The various reporting entities transmit in manners analogous to reporting entities discussed elsewhere herein. For example, transmitting in response to schedules received, schedules derived, and/or queries received from federated log creation agent 914, and/or transmitting using either or both public key and private key encryption techniques and/or decoding previously encrypted data, using either or both public key and private key encryption techniques, prior to the transmitting.

With reference now to FIG. 13, shown is an exemplary exploded view of federated log 916. Federated log 916 is shown to contain aggregations of content logs drawn from first-administered set 1000 of motes and second-administered set 1002 of motes. Shown is that federated log 916 contains aggregated sensing/control and routing/spatial logs for motes addressed 1A and 2A under the administration of a first network administrator. Depicted is that federated log 916 contains aggregated sensing/control and routing/spatial logs for motes addressed 3A and 4A under the administration of a second network administrator. Although aggregations for only two administered networks are shown, those having skill in the art will appreciate that in some implementations the number of administered networks logged could be several. In addition, although each individual administrator-specific aggregation is shown containing entries for only three motes, those having skill in the art will appreciate that in most implementations the number of motes in the aggregations will run to the hundreds, thousands, and/or higher.

B. Process(es) and/or Scheme(s)

With reference now again to FIGS. 2, 3, . . . , and/or FIG. 13, the depicted views may serve as a context for introducing one or more processes and/or devices described herein. Some exemplary processes include the operations of obtaining at least a part of a first-administered content log from a first set of motes; obtaining at least a part of a second-administered content log from a second set of motes; and creating a federated log from at least a part of the first-administered content log and at least a part of the second-administered content log. Other more general exemplary processes of the foregoing specific exemplary processes are taught at least in the claims and/or elsewhere in the present application.

In some specific exemplary processes, the operation of obtaining at least a part of a first-administered content log from a first set of motes includes but is not limited to the operation of receiving at least a part of one or more multi-mote content logs of the first set of motes. For example, federated log creation agent 914 receiving at least a part of the multi-mote content log 752 of mote 6A (e.g., such as shown and described in relation to FIGS. 7, 8, . . . , and/or 13).

In some specific exemplary processes, the operation of receiving at least a part of one or more multi-mote content logs of the first set of motes includes but is not limited to the operation of receiving at least a part of at least one of a mote-addressed sensing/control log from at least one aggregation of one or more first-administered logs. For example, federated log creation agent 914 receiving at least a part of aggregation of first-administered log(s) 910 as transmitted by first-administered reporting entity 902 for first-administered set 1000 of motes (e.g., as shown and/or described in relation to FIGS. 7, 8, . . . , and/or 13).

In some specific exemplary processes, the operation of receiving at least a part of one or more multi-mote content logs of the first set of motes includes but is not limited to the operation of receiving at least a part of a mote-addressed routing/spatial log from at least one aggregation of one or more first-administered logs. For example, federated log creation agent 914 receiving at least a part of aggregation of first-administered log(s) 910 as transmitted by first-administered reporting entity 902 for first-administered set 1000 of motes (e.g., as shown and/or described in relation to FIGS. 7, 8, . . . , and/or 13).

In some specific exemplary processes, the operation of receiving at least a part of one or more multi-mote content logs of the first set of motes includes but is not limited to the operation of receiving at least a part of at least one of a mote-addressed sensing log or a mote-addressed control log from a multi-mote reporting entity at a mote of the first set of motes. For example, federated log creation agent 914 receiving at least a part of one or more multi-mote content logs of first-administered set 1000 of motes from one or more multi-mote content logs' associated multi-mote reporting entities (e.g., such as shown and/or described in relation to the multi-mote content logs and/or associated reporting entities of first-administered set 800 of motes of FIGS. 7, 8, . . . , and/or 13).

In some specific exemplary processes, the operation of receiving at least a part of one or more multi-mote content logs of the first set of motes includes but is not limited to the operation of receiving at least a part of a mote-addressed routing/spatial log from a multi-mote reporting entity at a mote of the first set of motes. For example, federated log creation agent 914 receiving at least a part of a mote-addressed routing/spatial log from a multi-mote reporting entity at a mote of the first-administered set 1000 of motes (e.g., such as shown and/or described in relation to the multi-mote content log of mote 6A of FIGS. 7, 8, . . . , and/or 13).

In some specific exemplary processes, the operation of obtaining at least a part of a first-administered content log from a first set of motes includes but is not limited to the operation of receiving at least a part of at least one of a mote-addressed sensing/control log from a reporting entity at a mote of the first set of motes. For example, federated log creation agent 914 receiving at least a part of a mote-addressed sensing log/control log from one or more associated reporting entities at the motes of first-administered set 800 of motes (e.g., such as shown and/or described in relation the mote-addressed content logs of motes 3A and/or 5A of FIGS. 7, 8, . . . , and/or 13).

In some specific exemplary processes, the operation of obtaining at least a part of a first-administered content log from a first set of motes includes but is not limited to the operation of receiving at least a part of a mote-addressed routing/spatial log from a reporting entity at a mote of the first set of motes. For example, federated log creation agent 914 receiving at least a part of a mote-addressed routing/spatial log from one or more associated reporting entities at the motes of first-administered set 1000 of motes (e.g., such as shown and/or described in relation to the mote-addressed content logs of motes 3A and/or 5A of 7, 8, . . . , and/or 13).

In some specific exemplary processes, the operation of obtaining at least a part of a second-administered content log from a second set of motes includes but is not limited to the operation of receiving at least a part of one or more multi-mote content logs of the second set of motes. For example, federated log creation agent 914 receiving at least a part of the multi-mote content log associated with a mote of second-administered set 1002 of motes (e.g., such as shown and/or described in relation to FIGS. 10, 11, 12 and/or 13).

In some specific exemplary processes, the operation of receiving at least a part of one or more multi-mote content logs of the second set of motes includes but is not limited to the operation of receiving at least a part of at least one of a mote-addressed sensing log/control log from at least one aggregation of one or more second-administered logs. For example, federated log creation agent 914 receiving at least a part of aggregation of second-administered log(s) 912 as transmitted by second-administered reporting entity 904 for second-administered set 1002 of motes (e.g., as shown and/or described in relation to FIGS. 10, 11, 12, and/or 13).

In some specific exemplary processes, the operation of receiving at least a part of one or more multi-mote content logs of the second set of motes includes but is not limited to the operation of receiving at least a part of a mote-addressed routing/spatial log from at least one aggregation of one or more second-administered logs. For example, federated log creation agent 914 receiving at least a part of aggregation of second-administered log(s) 912 transmitted by second-administered reporting entity 904 for second-administered set 1002 of motes (e.g., as shown and described in relation to FIGS. 10, 11, 12, and/or 13).

In some specific exemplary processes, the operation of receiving at least a part of one or more multi-mote content logs of the second set of motes includes but is not limited to the operation of receiving at least a part of at least one of a mote-addressed sensing/control log from a multi-mote reporting entity at a mote of the second set of motes. For example, federated log creation agent 914 receiving at least a part of one or more multi-mote content logs of second-administered set 1002 of motes from one or more multi-mote content logs' associated multi-mote reporting entities (e.g., such as shown and described in relation to the multi-mote content logs and/or reporting entities of second-administered set 1002 of motes of FIGS. 10, 11, 12 and/or 13).

In some specific exemplary processes, the operation of receiving at least a part of one or more multi-mote content logs of the second set of motes includes but is not limited to the operation of receiving at least a part of a mote-addressed routing/spatial log from a multi-mote reporting entity at a mote of the second set of motes. For example, federated log creation agent 914 receiving at least a part of a mote-addressed routing/spatial log from a multi-mote reporting entity at a mote of the second-administered set 1002 of motes from an associated multi-mote reporting entity (e.g., such as shown and described in relation to the multi-mote content logs and/or reporting entities of second-administered set 1002 of motes of FIGS. 10, 11, 12, and/or 13).

In some specific exemplary processes, the operation of obtaining at least a part of a second-administered content log from a second set of motes includes but is not limited to the operation of receiving at least a part of at least one of a mote-addressed sensing/control log from a reporting entity at a mote of the second set of motes. For example, federated log creation agent 914 receiving at least a part of a mote-addressed sensing/control log from one or more associated reporting entities at the motes of second-administered set 1002 of motes (e.g., such as shown and described in relation the mote-addressed content logs and associated reporting entities of second-administered set 1002 of motes of FIGS. 10, 11, 12 and/or 13).

In some specific exemplary processes, the operation of obtaining at least a part of a second-administered content log from a second set of motes includes but is not limited to the operation of receiving at least a part of a mote-addressed routing/spatial log from a reporting entity at a mote of the second set of motes. For example, federated log creation agent 914 receiving at least a part of a mote-addressed routing/spatial log from one or more associated reporting entities at the motes of second-administered set 1002 of motes (e.g., such as shown and described in relation the mote-addressed content logs of second-administered set 1002 of motes of FIGS. 10, 11, 12, and/or 13).

In some specific exemplary processes, the operation of creating a federated log from at least a part of the first-administered content log and at least a part of the second-administered content log includes the operation of federated log creation agent 914 generating federated log 916 in response to one or more logs (e.g., multi-mote and/or mote-addressed logs) obtained from both first-administered set 1000 of motes and the second-administered set 1002 of motes. In some implementations, federated log creation agent 914 creates federated log 916 to include at least a part of a content log from two differently-administered mote networks, such as first-administered set 1000 of motes and second-administered set 1002 of motes (see., e.g., federated log 916 of FIG. 13). In some implementations, federated log creation agent 914 creates federated log 916 to include one or more entries denoting one or more respective administrative domains of one or more content log entries (e.g., see federated log 916 of FIG. 13). In other implementations, federated log creation agent 914 creates federated log 916 to include access information to one or more content logs for an administered content log (e.g., in some implementations, this is actually in lieu of a content log). In other implementations, federated log creation agent 914 creates federated log 916 to include information pertaining to a currency of at least one entry of an administered content log. In other implementations, federated log creation agent 914 creates federated log 916 to include information pertaining to an expiration of at least one entry of an administered content log. In other implementations, federated log creation agent 914 creates federated log 916 to include metadata pertaining to an administrative domain, wherein the metadata includes at least one of an ownership indicator, an access right indicator, a log refresh indicator, or a predefined policy indicator. In other implementations, federated log creation agent 914 creates federated log 916 to include an administrative domain-specific query string generated for or supplied by an administrative domain to produce an updated content log for that domain.

In some specific exemplary processes, the operation of creating a federated log from at least a part of the first-administered content log and at least a part of the second-administered content log includes but is not limited to the operations of creating the federated log from at least a part of one or more multi-mote content logs of the first set of motes; creating the federated log from at least a part of at least one of a mote-addressed sensing/control log or a mote-addressed routing log/spatial log of the first set of motes; creating the federated log from at least a part of one or more multi-mote content logs of the second set of motes; and/or creating the federated log from at least a part of at least one of a mote-addressed sensing/control log or a mote-addressed routing log/spatial log of the second set of motes. For example, federated log creation agent 914 creating at least a part of federated log 916 in response to portions of multi-mote content logs (e.g., multi-mote logs and/or aggregations of logs) received from reporting entities associated with first-administered set 1000 of motes and/or second-administered set 1002 of motes (e.g., such as shown and described in relation to FIGS. 10, 11, 12, and/or 13).

With reference now again to FIGS. 2, 3, . . . , and/or 13, the depicted views may yet again serve as a context for introducing one or more processes and/or devices described herein. Some specific exemplary processes include the operations of creating one or more first-administered content logs for a first set of motes; obtaining at least a part of the one or more first-administered content logs of the first set of motes; creating one or more second-administered content logs for a second set of motes; obtaining at least a part of the second-administered content logs of the second set of motes; and creating a federated log from at least a part of the one or more first-administered content logs and at least a part of the one or more second-administered content logs.

In some specific exemplary processes, the operations of creating one or more first-administered content logs for a first set of motes and creating one or more second-administered content logs for a second set of motes function substantially analogously as the processes described in creating mote-addressed content logs, mote-addressed logs, and aggregations of logs as set forth elsewhere herein (e.g., such as shown and/or described under Roman Numeral headings I (“MOTE-ASSOCIATED LOG CREATION”), III (“AGGREGATING MOTE-ASSOCIATED LOG DATA”), and V (“FEDERATING MOTE-ASSOCIATED LOG DATA”), above, as well as in the as-filed claims). Accordingly, the specific exemplary processes of the operations of creating one or more first-administered content logs for a first set of motes and creating one or more second-administered content logs for a second set of motes are not explicitly redescribed here for sake of clarity, in that such specific exemplary processes will be apparent to one of skill in the art in light of the disclosure herein (e.g., as shown and described under Roman Numeral headings I, III, and V, above, as well as in the as-filed claims).

In some specific exemplary processes, the operations of obtaining at least a part of the one or more first-administered content logs of the first set of motes; obtaining at least a part of the second-administered content logs of the second set of motes; and creating a federated log from at least a part of the one or more first-administered content logs and at least a part of the one or more second-administered content logs function substantially analogously as to like processes described elsewhere herein (e.g., as shown and described under Roman Numeral heading V (“FEDERATING MOTE-ASSOCIATED LOG DATA”), above, as well as in the as-filed claims). Accordingly, the specific exemplary processes of the operations of obtaining at least a part of the one or more first-administered content logs of the first set of motes; obtaining at least a part of the second-administered content logs of the second set of motes; and creating a federated log from at least a part of the one or more first-administered content logs and at least a part of the one or more second-administered content logs are not explicitly redescribed here for sake of clarity, in that such specific exemplary processes will be apparent to one of skill in the art in light of the disclosure herein (e.g., as shown and described under Roman Numeral heading V, above, as well as in the as-filed claims).

Those having skill in the art will recognize that the state of the art has progressed to the point where there is little distinction left between hardware and software implementations of aspects of systems; the use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software can become significant) a design choice representing cost vs. efficiency tradeoffs. Those having skill in the art will appreciate that there are various vehicles by which processes and/or systems described herein can be effected (e.g., hardware, software, and/or firmware), and that the preferred vehicle will vary with the context in which the processes are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a hardware and/or firmware vehicle; alternatively, if flexibility is paramount, the implementer may opt for a solely software implementation; or, yet again alternatively, the implementer may opt for some combination of hardware, software, and/or firmware. Hence, there are several possible vehicles by which the processes described herein may be effected, none of which is inherently superior to the other in that any vehicle to be utilized is a choice dependent upon the context in which the vehicle will be deployed and the specific concerns (e.g., speed, flexibility, or predictability) of the implementer, any of which may vary. Those skilled in the art will recognize that optical aspects of implementations will require optically-oriented hardware, software, and or firmware.

The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood as notorious by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, several portions of the subject matter subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in standard integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and/or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies equally regardless of the particular type of signal bearing media used to actually carry out the distribution. Examples of a signal bearing media include, but are not limited to, the following: recordable type media such as floppy disks, hard disk drives, CD ROMs, digital tape, and computer memory; and transmission type media such as digital and analog communication links using TDM or IP based communication links (e.g., packet links).

In a general sense, those skilled in the art will recognize that the various aspects described herein which can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or any combination thereof can be viewed as being composed of various types of “electrical circuitry.” Consequently, as used herein “electrical circuitry” includes, but is not limited to, electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, electrical circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes and/or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes and/or devices described herein), electrical circuitry forming a memory device (e.g., forms of random access memory), and/or electrical circuitry forming a communications device (e.g., a modem, communications switch, or optical-electrical equipment).

Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use standard engineering practices to integrate such described devices and/or processes into mote processing systems. That is, at least a portion of the devices and/or processes described herein can be integrated into a mote processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical mote processing system generally includes one or more of a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, user interfaces, drivers, sensors, actuators, applications programs, one or more interaction devices, such as USB ports, control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity; control motors for moving and/or adjusting components and/or quantities). A typical mote processing system may be implemented utilizing any suitable available components, such as those typically found in mote-appropriate computing/communication systems, combined with standard engineering practices. Specific examples of such components include commercially described components such as Intel Corporation's mote components and supporting hardware, software, and firmware.

The foregoing described aspects depict different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely exemplary, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality.

While particular aspects of the present subject matter described herein have been shown and described, it will be obvious to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from this subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of this subject matter described herein. Furthermore, it is to be understood that the invention is defined by the appended claims. It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should NOT be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to inventions containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” and/or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense of one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together). In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense of one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and A, B, and/or C together). 

1. A method comprising: determining at least one of sensing information or control information of a device at a mote; obtaining a time stamp of the at least one of sensing information or control information; and creating one or more mote-addressed content logs with the obtained time stamp and having at least one device identifier associated with the device.
 2. The method of claim 1, wherein said determining at least one of sensing information or control information of a device at a mote further comprises: accessing at least one device entity registry.
 3. The method of claim 2, wherein said accessing at least one device entity registry further comprises: receiving at least one device entity identifier; and storing the at least one device identifier to a device entity registry.
 4. The method of claim 1, wherein said determining at least one of sensing information or control information of a device at a mote further comprises: communicating with at least one device-associated entity.
 5. The method of claim 4, wherein said communicating with at least one device-associated entity further comprises: communicating with at least one of a light device entity, an electrical device entity, a pressure device entity, a temperature device entity, a volume device entity, an inertial device entity, or an antenna entity.
 6. The method of claim 4, wherein said communicating with at least one device-associated entity further comprises: accessing at least one device identifier.
 7. The method of claim 1, wherein said determining at least one of sensing information or control information of a device at a mote further comprises: communicating with at least one device entity using a common application protocol.
 8. The method of claim 1, wherein said creating one or more mote-addressed content logs having at least one device identifier associated with the device in response to said determining further comprises: creating at least one mote-addressed content log at the mote.
 9. The method of claim 1, wherein said creating one or more mote-addressed content logs having at least one device identifier associated with the device in response to said determining further comprises: creating at least one extensible log.
 10. The method of claim 9, wherein said creating at least one extensible log further comprises: creating the at least one extensible log in response to a type of content logged.
 11. The method of claim 1, further comprising: aggregating the one or more created mote-addressed content logs from an initial time to current time comprising obtaining time entries corresponding with the time stamp of the one or more mote-addressed logs. 